feat(react-router): server action revalidation opt out via $SKIP_REVALIDATION field.
#14154
Conversation
🦋 Changeset detectedLatest commit: 7515942 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
MichaelDeBoey
changed the title
$NO_REVALIDATE field.$NO_REVALIDATE field.
jacob-ebey
force-pushed
the
rsc-no-revalidate
branch
from
07ddf5f to
9b4ea5a
Compare
jacob-ebey
force-pushed
the
rsc-no-revalidate
branch
from
9b4ea5a to
e6e60a6
Compare
jacob-ebey
force-pushed
the
rsc-no-revalidate
branch
from
e6e60a6 to
28a7351
Compare
jacob-ebey
changed the title
$NO_REVALIDATE field.$SKIP_REVALIDATION field.
| filterMatchesToLoad || null, | ||
| "filterMatchesToLoad" in opts | ||
| ? (opts.filterMatchesToLoad ?? null) | ||
| : null, |
There was a problem hiding this comment.
I think we want to fall back on the original value here if they didn't pass an override?
| : null, | |
| : (filterMatchesToLoad ?? null), |
I should go through and clean up some of the null/undefined stuff in here one of these days 😬
There was a problem hiding this comment.
actually we need it for the first half of the ternary in case they specified an undefined key - they shouldn't, but the types would allow it. Maybe this is easier?
opts.filterMatchesToLoad ?? filterMatchesToLoad ?? null,
There was a problem hiding this comment.
It's different behavior. It should be "if provided, use it (undefined, null, new imp), otherwise use default", we need the key check for that.
No description provided.